Output information providing method, output information providing system, document outputting method, and document outputting system

ABSTRACT

In an output information providing method for providing an edit property indicating edit contents executable for a document and an output property indicating an output method executable when the document is output, an output condition property candidate obtain request is received, and the output condition property candidate is provided to a request originator sending the output condition property candidate obtain request.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to output information providingmethods, output information providing systems, document outputtingmethods, and document outputting systems for editing and outputting adocument.

2. Description of the Related Art

Conventionally, a document can be printed out by using a printer or anMFP (Multi-Function Printer) connected to a network through a personalcomputer (hereinafter, called PC). Recently, in addition to the abovefunctions, various services have been developed and provided as Webservices. In this case, various services as the Web services arerealized by an application loaded in the PC serving as a client withrespect to the Web services.

As described above, conventionally, the application loaded in the clientPC serves as the client with respect to each of the Web services. Thus,it is possible to architect the application suitable for variousrequirements. However, the application is required to send and receiveinformation to/from each of the Web services, which is subject toinquire what kind of edit can be performed or to notify edit contents.That is, the client PC is required to communicate with a plurality ofthe Web services.

SUMMARY OF THE INVENTION

It is a general object of the present invention to provide outputinformation providing methods, output information providing systems,document outputting methods, and document outputting systems, in whichthe above-mentioned problems are eliminated.

A more specific object of the present invention is to provide an outputinformation providing method, an output information providing system, adocument outputting method, and a document outputting system, in thatclient PC can effectively output a document and send and receiveinformation concerning an edit to/from a Web service.

The above objects of the present invention are achieved by an outputinformation providing method for providing an edit property indicatingedit contents executable for a document and an output propertyindicating an output method executable when the document is output, theoutput information providing method including: receiving an outputcondition property candidate obtain request for obtaining an outputcondition property candidate; and providing the output conditionproperty candidate to a request originator sending the output conditionproperty candidate obtain request.

The above objects of the present invention are achieved by an outputinformation providing system for providing an output condition propertycandidate including an edit property indicating edit contents executablewith respect to a document and an output property indicating an outputmethod executable when the document is output, to a client requestingediting or outputting the document, the output information providingsystem including: an output condition property candidate obtain requestreceiving part receiving an output condition property candidate obtainrequest for obtaining an output condition property candidate from theclient; and an output condition property candidate providing partproviding the output condition property candidate to the client.

The above objects of the present invention are achieved by a documentoutputting method for editing and outputting a document, including:receiving an output condition property candidate obtain requestincluding an output property indicating an outputting method executablewhen the document is output; providing the output condition propertycandidate to a request originator sending the output condition propertycandidate; receiving a document output request including an outputcondition being selected from the output condition property; editing thedocument based on the output condition; and outputting the documentbeing edited based on the output condition.

The above objects of the present invention are achieved by a documentoutputting system for providing an edit property indicating editcontents executable for a document and an output property indicating anoutputting method executable when the document is output to a clientrequesting outputting the document, the document outputting systemincluding: an output property candidate obtain request receiving partreceiving an output property candidate obtain request for obtaining anoutput condition property candidate from the client; an output conditionproperty candidate providing part providing the output conditionproperty candidate to the client; a document output request receivingpart receiving a document output request including an output conditionbeing selected from the output condition property candidate; an editingservice part editing the document based on the output condition; and anoutputting service part outputting the document being edited based onthe output condition.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following, embodiments of the present invention will be describedwith reference to the accompanying drawings.

FIG. 1 is a block diagram showing a configuration of a documentprocessing system 100 according to the present invention;

FIG. 2 is a block diagram showing a functional configuration of amulti-functional apparatus according to the present invention;

FIG. 3 is a block diagram showing a hardware configuration of themulti-functional apparatus according to the present invention;

FIG. 4 is a block diagram showing a hardware configuration of a clientPC according to the present invention;

FIG. 5 is a block diagram showing a system configuration according to afirst embodiment of the present invention;

FIG. 6 is a block diagram showing a functional configuration in thesystem configuration according to the first embodiment of the presentinvention;

FIG. 7 is a diagram showing a sequence flow according to the firstembodiment of the present invention;

FIG. 8 is a diagram showing an example of a print property according tothe first embodiment of the present invention;

FIG. 9 is a diagram showing an example of an edit property according tothe first embodiment of the present invention;

FIG. 10 is a flowchart for explaining a process for generating a printcondition property candidate according to the first embodiment of thepresent invention;

FIG. 11 is a flowchart for explaining the process for generating theprint condition property candidate according to the first embodiment ofthe present invention;

FIG. 12 is a diagram showing a first process according to the firstembodiment of the present invention;

FIG. 13 is a diagram showing a SOAP message in a case in that a clientPC indicates an image editing service, according to the first embodimentof the present invention;

FIG. 14 is a diagram showing a SOAP message in a case in that the imageediting service is predetermined beforehand to use, according to thefirst embodiment of the present invention;

FIG. 15 is a diagram showing an example of the print condition propertycandidate according to the first embodiment of the present invention;

FIG. 16 is a diagram showing another example the print conditionproperty candidate according to the first embodiment of the presentinvention;

FIG. 17 is a diagram showing a second process according to the firstembodiment of the present invention;

FIG. 18 is a diagram showing an example of a SOAP message including animage editing service candidate according to the first embodiment of thepresent invention;

FIG. 19 is a diagram showing another SOAP message including the editcapability according to the first embodiment of the present invention;

FIG. 20 is a diagram showing a screen to set a print function and anadvanced function, according to the first embodiment of the presentinvention;

FIG. 21 is a diagram showing a sequence flow for explaining the processfor printing a document according to the first embodiment of the presentinvention;

FIG. 22 is a diagram showing the sequence flow for explaining theprocess for printing a document according to the first embodiment of thepresent invention;

FIG. 23 is a diagram showing an example of the SOAP message informed bya sdocument print request according to the first embodiment of thepresent invention;

FIG. 24 is a flowchart for explaining a process conducted by a printingWS according to the first embodiment of the present invention;

FIG. 25 is a diagram showing a prototype of a function used by in stepS108 in FIG. 21, according to the first embodiment of the presentinvention;

FIG. 26 is a diagram showing a SOAP message showing a document editrequest according to the first embodiment of the present invention;

FIG. 27 is a diagram showing a SOAP message showing an edit resultnotice according to the first embodiment of the present invention;

FIG. 28 is a diagram showing a SOAP message for a document print acceptresult according to the first embodiment of the present invention;

FIG. 29 is a diagram showing a system configuration according to asecond embodiment of the present invention;

FIG. 30 is a diagram showing a functional configuration according to thesecond embodiment of the present invention;

FIG. 31 is a diagram showing a sequence flow of a process for obtainingthe print condition property candidate according to the secondembodiment of the present invention;

FIG. 32 is a diagram showing a sequence flow of a process concerning aprint according to the second embodiment of the present invention;

FIG. 33 is a diagram showing the sequence flow of the process concerninga print according to the second embodiment of the present invention;

FIG. 34 is a diagram showing a SOAP message for a document print requestaccording to the second embodiment of the present invention;

FIG. 35 is a block diagram showing a system configuration according to athird embodiment of the present invention;

FIG. 36 is a block diagram showing a functional configuration accordingto the third embodiment of the present invention;

FIG. 37 is a diagram showing a sequence flow of a process concerning aprint, according to the third embodiments of the present invention;

FIG. 38 is a diagram showing a sequence flow of the process concerning aprint, according to the third embodiments of the present invention;

FIG. 39 is a diagram showing a SOAP message for a document ticket createrequest according to the third embodiment of the present invention;

FIG. 40 is a diagram showing the SOAP message for a response withrespect to the document ticket create request according to the thirdembodiment of the present invention;

FIG. 41 is a block diagram showing a system configuration according to afourth embodiment of the present invention;

FIG. 42 is a block diagram showing a functional configuration accordingto the fourth embodiment of the present invention;

FIG. 43 is a diagram showing a sequence flow of a process concerning aprint according to the fourth embodiment of the present invention;

FIG. 44 is a diagram showing the sequence flow of the process concerninga print according to the fourth embodiment of the present invention;

FIG. 45 is a diagram showing a system configuration according to a fifthembodiment of the present invention;

FIG. 46 is a block diagram showing a functional configuration accordingto the fifth embodiment of the present invention;

FIG. 47 is a diagram showing a sequence flow of a process for obtaininga print condition property according to the fifth embodiment of thepresent invention;

FIG. 48 is a diagram showing a sequence flow of a process concerning aprint according to the fifth embodiment of the present invention;

FIG. 49 is a diagram showing the sequence flow of the process concerningthe print according to the fifth embodiment of the present invention;

FIG. 50 is a block diagram showing a system configuration according to asixth embodiment of the present invention;

FIG. 51 is a diagram showing a functional configuration according to thesixth embodiment of the present invention;

FIG. 52 is a diagram showing a sequence flow of the process forobtaining a print condition property candidate according to the seventhembodiment of the present invention;

FIG. 53 is a diagram showing a sequence flow of a process concerning aprint according to the sixth embodiment of the present invention:

FIG. 54 is a diagram showing the sequence flow of the process concerninga print according to the sixth embodiment of the present invention:

FIG. 55 is a block diagram showing a system configuration according to aseventh embodiment of the present invention;

FIG. 56 is a diagram showing a functional configuration according to theseventh embodiment of the present invention;

FIG. 57 is a diagram showing a sequence flow of a process for obtainingthe print condition property according to the seventh embodiment of thepresent invention;

FIG. 58 is a diagram showing a sequence flow of a process concerning aprint according to the seventh embodiment of the present invention;

FIG. 59 is a diagram showing the sequence flow of the process concerninga print according to the seventh embodiment of the present invention;

FIG. 60 is a block diagram showing a system configuration according toan eighth embodiment of the present invention;

FIG. 61 is a diagram showing a functional configuration according to theeighth embodiment of the present invention;

FIG. 62 is a diagram showing a sequence flow of a process for obtaininga print condition property candidate according to the eighth embodimentof the present invention;

FIG. 63 is a diagram showing a sequence flow of a process concerning aprint according to the eighth embodiment of the present invention;

FIG. 64 is a diagram showing the sequence flow of the process concerninga print according to the eighth embodiment of the present invention;

FIG. 65 is a diagram showing a configuration in that a single Webservice client (WSC) can use a plurality of Web services (WS), accordingto the present invention;

FIG. 66 is a diagram showing another configuration in that a single Webservice can use a plurality of Web service client (WSC), according tothe present invention; and

FIG. 67 is a diagram showing a configuration formed by the MFP-Adescribed in FIG. 65 and the MFP-B described in FIG. 66, according tothe present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

In the following, embodiments of the present invention will be describedwith reference to the accompanying drawings. In the embodiments of thepresent invention, a document processing system is described as anoutput information providing system, and a case in that an output of adocument is a print will be described. Accordingly, “output” is read as“print”. For example, in the following embodiments, an output propertycan be read as a print property. Also, in the following, for example,“obtain” includes a meaning of “generate”.

Moreover other outputs, for example, an output by a facsimiletransmission, a distribution to other computers, and a like can beconsidered.

Furthermore, in the following, “image” and “document” are used. Adocument includes one or more images and bibliographic information.Accordingly, in the following embodiments, to edit and print out adocument expresses to edit and print out an image included in thedocument. Even if an expression of editing and printing out a documentis used, the image included in the document can be edited and printedout.

[Overview]

First, the document processing system according to the present inventionwill be described with reference to FIG. 1. In FIG. 1, a documentprocessing system 100 includes a printing service 210 as a Web service,an image editing service 211 as a Web service, a document managementservice 212 as a Web service, and at least one client PC (PersonalComputer) 213, which can communicate with each other. As shown in FIG.1, documents 301 and 302 are sent and received among services 210, 211,and 212. The document management service 212 includes a document DB(database) 214.

The client PC 213 is a personal computer which a user uses to editand/or print out a document, and includes an application to use theabove-described services 210, 211, and 212.

The printing service 210 receives a document print request from theclient PC 213, prints out the document, and provides a print propertyshowing a printing method executable when printing out the document inresponse to a request sent from the client PC 213.

The image editing service 211 is a service for editing a document, andprovides an edit property showing edit contents being executable withrespect to the document. The document management service 212 manages thedocument by using the document DB 214.

As described above, the Web services 210, 211, and 212 send and receiveinformation such as the document, the edit property, and the liketo/from each other.

As described above, the printing service 210, the image editing service211, and the document management service 212 may not be specificapparatuses, but represent elements of the document processing system100. Accordingly, the printing service 210, the image editing service211, and the document management service 212 may be implemented indifferent apparatuses, respectively or in a single apparatus.

Therefore, in each of the following embodiments, different combinationsof the Web services and apparatuses will be described. Prior to eachexplanation of the following embodiment, a multi-functional apparatusimplementing the above-described Web services 210, 211, and 212, and theclient PC 213 will be described according to the present invention.

FIG. 2 is a block diagram showing a functional configuration of themulti-functional apparatus according to the present invention. Themulti-functional apparatus 1 includes a software group 2, a boot part 3,and hardware resources 4.

The boot part 3 is executed first when the multi-functional apparatus 1is turned on, and activates an application layer 5, and a platform layer6. For example, the boot part 3 reads out programs of the applicationlayer 5 and the platform layer 6 from an HDD (Hard Disk Drive) or alike, and transfers the programs read out from the HDD or the like to amemory area. The hardware resources 4 include a scanner 11, a plotter12, and another hardware resource 13 such as an ADF (Auto DocumentFeeder).

The software group 2 includes the application layer 5 and the platformlayer 6 being activated on an operating system (hereinafter, called OS)such as UNIX>. The application layer 5 includes programs to conduct eachspecific process for a user service concerning an image formation suchas a printer, a copier, a facsimile, a scanner, and a like.

The application layer 5 includes a printer application 21 being anapplication for the printer, a copy application 22 being an applicationfor the copy, a FAX application 23 being an application for thefacsimile, a scanner application 24 being an application for thescanner, a WEB page application 25, a SOAP (Simple Object AccessProtocol) communication application 26, at least one or more commonfunction (hereinafter, called SFs (Service Functions)) 28 and 29, and aWEB service function (hereinafter, called WSF) provided between the WEBpage application 25 and the SOAP communication application 26, and theSFs 28 and 29.

The WSF 27 includes an application program interface (hereinafter,called WS-API) 51 to receive a process request from the WEB pageapplication 25 and the SOAP communication application 26 by functionsbeing defined beforehand. Also, the SFs 28 and 29 include an applicationprogram interface (hereinafter, called SF-API) 52 to receive a processrequest from the WSF 27 by a function being defined beforehand.

When the WSF 27 receives the process request from the WEB pageapplication 25 and the SOAP communication application 26 through theWS-API 51, the WSF 27 selects one of the SFs 28 and 29 in response tothe process request. The WSF 27 sends the process request receivedthrough the WS-API 51 to the selected one of the SFs 28 and 29 throughthe SF-API 52. When the selected one of the SFs 28 and 29 receives theprocess request through the SF-API 52, the selected one of the SFs 28and 29 conducts a process corresponding to the process request. The SOAPcommunication application 26 generates and interprets a SOAP message asa server of the Web service 210, 211, or 212.

The platform layer 6 includes a control service layer 9 for interpretingthe process request received from the application layer 6 and forcreating an acquisition request for acquiring the hardware resources 4,a system resources manager (hereinafter, called SRM) 39 for mediatingthe acquisition request received from the control service layer 9 bymanaging one or more hardware resources 4, and a handler layer 10 formanaging the hardware resources 4 in response to the acquisition requestreceived from the SRM 39.

The control service layer 9 includes at least one of service modulessuch as a network control service (hereinafter, called NCS) 31, adelivery control service (hereinafter, called DCS) 32, an operationpanel control service (hereinafter, called OCS) 33, a certificationcontrol service (hereinafter, called CCS) 34, an engine control service(hereinafter, called ESC) 35, a memory control service (hereinafter,called MCS) 36, a user information control service (hereinafter, calledUCS) 37, a system control service (hereinafter, called SCS) 38, and alike.

The platform layer 6 includes an application program interface(hereinafter, called API) 53 for receiving the process request from theapplication layer 6 by a function being defined beforehand. The OSexecutes software for the application layer 5 and the platform layer 6as processes in parallel.

A process of the NCS 31 provides a service for applications requiring anetwork I/O to use in common. The process of the NCS 31 distributes datareceived from each protocol at a network side to a relative application,and intermediates to send data from each application to the networkside.

For example, the NCS 31 controls a data communication with a networkdevice connected through a network in accordance with an HTTP (HyperTextTransfer Protocol) by an httpd (HyperText Transfer Protocol Daemon) Aprocess of the DSC 32 controls a distribution of accumulated documents.A process of the OCS 33 controls an operation panel, which is aninformation transmitting part between an operator and a main unitcontrol of the multi-functional apparatus 1. A process of the CCS 34conducts a process concerning a user certification.

A process of the ECS 35 controls an engine part such as the scanner 11,the plotter 12, and the another hardware resource 13. A process of theMCS 36 acquires and releases a memory area, and conducts a memorycontrol to control use of the HDD. A process of UCS 37 manages userinformation.

A process of the SCS 38 conducts processes such as an applicationmanagement, an operation panel control, a system screen display, an LEDdisplay, a hardware resource management, an interruption control of theapplications, and a like.

A process of the SRM 39 conducts the system control with the SCS 38, andmanages the hardware resources 4. For example, the process of the SRM 39mediates the acquisition request from an upper layer using the hardwareresources 4, and conducts an execution control.

In detail, the process of the SRM 39 determines whether or not one ofthe hardware resources 4, which corresponds to the acquisition request,is available (is used by another acquisition request). If available, theprocess of the SRM 39 informs the upper layer that the one of thehardware resources 4 to which the acquisition request is made isavailable. Also, the process of the SRM 39 schedules to use the hardwareresources 4 with respect to the acquisition request received from theupper layer, and directly conducts various operations in accordance withrequest contents (for example, a sheet feed and an image creatingoperation, a memory acquisition, a file generation, and a like).

A handler layer 10 includes a FAX control unit handler (hereinafter,called FCUH) 40 for managing a FAX control unit (hereinafter, calledFCU), which will be described later, and an image memory handler(hereinafter, called IMH) 41 for assigning the memory area to a processand managing the memory area being assigned to the process. The SRM 39and the FCUH 40 conduct a process request with respect to the hardwareresources 4 by using an engine I/F (InterFace) 54, which can send theprocess request with respect to the hardware resources 4 by a functionbeing defined beforehand.

The multi-functional apparatus 1 can centralize and process in commonamong the applications at the platform layer 6. Next, a hardwareconfiguration of the multi-functional apparatus 1 will be described withreference to FIG. 3.

FIG. 3 is a block diagram showing the hardware configuration of themulti-functional apparatus according to the present invention. Themulti-functional apparatus 1 includes a controller board 60, anoperation panel 59, the FCU 68, and an engine 71. Moreover, the FCU 68includes a G3 standard support unit 69, and a G4 standard support unit70.

Moreover, the controller board 60 includes a CPU (Central ProcessingUnit) 61, an ASIC (Application Specific Integrated Circuit) 66, an HDD(Hard Disk Drive) 65, a system memory (MEM-P) 63, a local memory (MEM-C)64, a north bridge (hereinafter, called NB) 62, a south bridge(hereinafter, called SB) 73, a NIC (Network Interface Card) 74, a USB(Universal Serial Bus) device 75, an IEEE 1394 device 76, and acentronics™ device 77.

The operation panel 59 is connected to the ASIC 66 of the controllerboard 60. The SB 73, the USB device 75, the IEEE 1394 device 76, and thecentronics™ device 77 are connected to the NB 62 through a PCI bus 79.

The FCU 68 and the engine 71 are connected to the ASIC 66 of thecontroller board 60 through a PCI bus 78.

The controller board 60 connects to the local memory (MEM-C) 64 of theASIC 66 and the HDD 65, and also connects to the CPU 61 and the ASIC 66through the NB 62 of a CPU chip set. As described above, since the CPU61 and the ASIC 66 are connected through the NB 62, this hardwareconfiguration can be realized even if an interface of the CPU 61 is notopened to the public.

Moreover, instead of connecting the ASIC 66 and the NB 62 to each otherthrough a PCI bus, the ASIC 66 and the NB 62 are connected through anAGP (Accelerated Graphics Port) 67. As described above, in order tocontrol executions of one or more processes forming the applicationlayer 5 and the platform layer 6, the ASIC 66 and the NB 62 areconnected to each other through the AGP 67 but not a PCI bus.Accordingly, it is possible to prevent from degrading performance of themulti-functional apparatus 1.

The CPU 61 controls the entire multi-functional apparatus 1. The CPU 61activates and executes the NCS 31, the DCS 32, the OCS 33, the CCS 34,the ECS 35, the MCS 36, the UCS 37, the SCS 38, the SRM 39, the FCUH 40,and the IMH 41 as processes on the OS, respectively. Moreover, the CPU61 activates and executes the printer application 21, the copyapplication 22, the FAX application 23, the scanner application 24, theWeb page application 25, and the SOAP communication application 26,which form the application layer 5.

The NB 62 is a bridge to connect the CPU 61, the system memory 63, theSB 73, and the ASIC 66 to each other. The system memory 63 is a memoryused as an drawing memory of the multi-functional apparatus 1. The SB 73is a bridge to connect the NB 62, the PCI bus 79, and a peripheraldevice to each other. Also, the local memory 64 is a memory used as adrawing buffer for a copy, a coding buffer, and a like.

The ASIC 66 is an IC (Integrated Circuit) for an image process includinghardware elements for the image process. Also, the HDD 65 is a storagefor accumulating image data, document data, programs, font data, forms,and a like. The operation panel 59 receives an input operation from auser and also displays information for the user.

Next, a hardware configuration of the client PC 213 in FIG. 1 will bedescribed with reference to FIG. 4.

As shown in FIG. 4, in the hardware configuration in FIG. 4, the clientPC 213 includes an input unit 122, a display unit 123, a drive unit 124for a recording medium 125, an auxiliary storage unit 126, a memory unit127, a CPU 120, and an interface unit 121.

The input unit 122 includes a keyboard and a mouse, and is used for auser to input various operation signals to the client PC 213. Thedisplay unit 123 displays various screens and data necessary for theuser to operate the client PC 213. The interface unit 121 is aninterface to connect the client PC 213 to a network or to connect toanother device. For example, the interface unit 121 includes the NIC(Network Interface Card), a modem, a USB (Universal Serial Bus), and alike.

A program for operating the client PC 213 is provided by the recordingmedium 125 such as a CD-ROM (Compact Disk-Read Only Memory) or a like orby downloading through the network. Also, the recording medium 125 isset to the drive unit 124, and then data and the program are installedinto the auxiliary storage unit 126 through the drive unit 124.

The auxiliary storage unit 126 stores the data and the program,necessary files, and a like. The memory unit 127 reads out and storesthe program from the auxiliary storage unit 126 when the computer systemis activated. The CPU 120 executes a process in accordance with theprogram read out from the auxiliary storage unit 126 and stored in thememory unit 127.

In the following, eight embodiments will be described. In the followingexplanations, parts that have been explained will be omitted. Also,parts that are the same as the ones are previously described by the samereference numerals and the explanation thereof will be omitted. Forexample, the NCS is denoted by the same reference numeral 31.

First Embodiment

In a first embodiment, most explanation will be about a processconcerning a print condition property candidate. A process concerning aprint will be described after the process concerning the print conditionproperty candidate is described.

FIG. 5 is a block diagram showing a system configuration according tothe first embodiment of the present invention. In the systemconfiguration shown in FIG. 5, a client PC 213, a printing service 210,an image editing service 211, and a document DB 214, and documents 301,302, and 303 are shown.

As shown in FIG. 5, in the first embodiment, a document subject to printout or edit is included in the client PC 213. Moreover, in FIG. 5, threedocuments 301, 302, and 303 are shown as documents to send and receive.Accordingly, in the first embodiment, sending and receiving thedocuments is performed three times.

Next, a functional configuration will be described with reference toFIG. 6 in detail. FIG. 6 is a block diagram showing the functionalconfiguration in the system configuration according to the firstembodiment of the present invention. In FIG. 6, the client PC 213, anMFP-A 221 as one multi-functional apparatus 1, and an MFP-B 222 asanother multi-functional apparatus 1 are shown.

The client PC 213 includes an application 229 having a user interfaceand a network interface 230.

The MFP-A 221 includes the NCS 31 having the httpd 223, a Web serviceserver (WSS) 224, a Web service client (WSC) 225, a printing WSF 226,the ECS 35, and the plotter 12. Also, the MFP-B 222 includes the NCS 31having the httpd 223, the Web service server (WSS) 224, an image editingWSF 227, and a storage area 228 for an image edit.

As described above, the application 229 is used when a user prints out adocument. The application 229 has a scheme for changing the userinterface in response to a tag in an XML (extensible Markup Language)sentence showing available service. This available service is shown bythe print condition property candidate, which will be described later.

The Web service server (WSS) 224 converts a SOAP request message sentfrom a Web service client such as the client PC 213 into an executionrequest of the Web service function (hereinafter, called WSF), and sendsthe execution request to a specific WSF. The Web service server (WSS)224 converts an execution result received from the WSF in the MFP-A 221(MFP-B 222) into a SOAP response message, and sends the SOAP responsemessage to the Web service client (client PC 213) that sent the SOAPrequest message.

The Web service client (WSC) 225 converts the execution request of theWeb service sent from the Web service or the application in the MFP-A221 (MFP-B222) into the SOAP request message, and sends the SOAP requestmessage to a specific Web service. The Web service client (WSC) 225analyses the SOAP response message sent from the Web service located inthe network, and sends a result to the Web service or the application inthe MFP-A 221 (MFP-B 222), which sent the SOAP request message. In thefirst embodiment, the Web service client (WSC) 225 provided in the MFP-B222 is not used.

The printing WSF 226 prints out a document by using the ECS 35. Theimage editing WSF 227 edits an image. For example, the storage area 228for the image edit is an area which is temporarily provided in the HDD65, the system memory 63, or the local memory 64.

In the above-described first embodiment, the Web service server (WSS)224 and the Web service client (WSC) 225 in FIG. 6 correspond to the Webpage application 25 and the SOAP communication application 26 in FIG. 2,respectively.

Next, a sequence flow for obtaining the print condition propertycandidate will be described with reference to FIG. 7. FIG. 7 is adiagram showing the sequence flow according to the first embodiment ofthe present invention. In the sequence flow in FIG. 7, a sequentialprocess, which is conducted among the client PC 213, the MFP-A 221, andthe MFP-B 222, are shown. In FIG. 7, a printing WS 240 collectivelyrepresents the Web service server (WSS) 224 and the printing WSF 226 inthe MFP-A 221 in FIG. 6. Also, an image editing WS 241 collectivelyrepresents the Web service server (WSS) 224 and the image editing WSF227 in the MFP-B 222 in FIG. 6.

In addition, the sequential process in the sequence flow shown in FIG. 7is a process for obtaining the print condition property candidate. Thisprint condition property candidate includes an edit property showing theedit contents executable for a document, and a print property showing aprinting method executable when the document is printed out. Theproperty and the print property will be described later.

The sequence flow will be described. In step S101, the client PC 213informs a print condition property candidate obtain request, which is anobtain request for obtaining the print condition property candidate, tothe printing WS 240. In step S102, the printing WS 240 informs a WSrequest send request, which requests sending a WS request to anindicated Web service, to the Web service client (WSC) 225. In thiscase, a URL (Uniform Resource Locater) of the image editing WS, and amethod name showing an edit property candidate obtain request areinformed with the WS request send request.

In step S103, the Web service client (WSC) 225 informs the edit propertycandidate obtain request to the image editing WS 241 by a SOAP message.In step S104, in response to this SOAP message, the image editing WS 241informs an edit property notice to the Web service client (WSC) 225 bythe SOAP message. By sending the edit property notice, the edit propertyis informed to the MFP-A 221. Processes in steps S103 and S104 in theimage editing WS 241 correspond to a step of obtaining an edit property.

In step S105, the Web service client (WSC) 225 informs a WS requestresult notice to the printing WS 240. In this case, the edit propertycandidate informed from the MFP-B 222 is also informed to the printingWS 240. When the edit property candidate is informed to the printing WS240, the printing WS 240 generates the print condition propertycandidate from the print property candidate held by the printing WS 240and the edit property candidate informed from the MFP-B 222. Thisprocess conducted by the printing WS 240 will be described in accordancewith a flowchart later.

In step S106, after the printing WS 240 generates the print conditionproperty candidate, the printing WS 240 informs the print conditionproperty candidate by the SOAP message.

By the above-described processes, the client PC 213 can obtain the printcondition property candidate.

Next, the print property and the edit property will be described indetail. FIG. 8 is a diagram showing an example of the print propertyaccording to the first embodiment of the present invention. As shown inFIG. 8, the print property includes “NUMBER OF COPIES”, “SHEET SIZE”,“BOTH SIDE PRINT YES/NO”, “COLLATE YES/NO”, and a like.

In the print property, “NUMBER OF COPIES” shows whether or not the usercan indicate the number of copies for a document. “SHEET SIZE” showswhether or not the user can indicate the size of sheet to print out.“BOTH SIDE PRINT YES/NO” shows whether or not the user can conduct aboth side print. “COLLATE YES/NO” shows whether or not the user cancollate each of copies of the document.

As shown in this example of the print property described above, basicavailable print options concerning a print are listed. Since the printproperty is obtained when the print condition property candidate isgenerated, for example, processes in step S105 and step S106 correspondto a print property obtaining step.

Next, the edit property will be described with reference to FIG. 9. FIG.9 is a diagram showing an example of the edit property according to thefirst embodiment of the present invention. As shown in FIG. 9, in theedit property, “PASTE CONFIDENTIAL STAMP”, “DRAWING OPERATION”,“DELETE/COPY/PASTE/MOVE/CONVERT COLOR FOR INDICATED AREA”, “CONTINUOUSLYEDIT MULTIPLE PAGES”, and “REMOVE STAIN OF GROUND” are listed.

“PASTE CONFIDENTIAL STAMP” shows whether or not the user can paste aconfidential stamp to a document and then print out the document withthe confidential stamp. “DRAWING OPERATION” shows whether or not theuser can draw a straight line, a broken line, a curved line, a polygon,a circle, and a letter. “DELETE/COPY/PASTE/MOVE/CONVERT COLOR FORINDICATED AREA” shows a list of processes with respect to the indicatedarea, and shows whether or not the user can delete the indicated area,copy the indicated area, paste the indicated area, move the indicatedarea, and convert a color of the indicated area. “CONTINUOUSLY EDITMULTIPLE PAGES” shows whether or not the user can continuously editmultiple pages. “REMOVE STAIN OF GROUND” shows whether or not the usercan remove a stain of a color of the document.

As shown in this example of the print property described above, it ispossible to conduct various edits with respect to the document. In otherembodiments described in the following, the print property and the editproperty will be used as the same manner, and the print property and theedit property will include the same contents.

Next, the process for generating the print condition property candidatedescribed above in FIG. 7 will be described with reference to FIG. 10and FIG. 11. FIG. 10 and FIG. 11 are flowcharts for explaining theprocess for generating the print condition property candidate accordingto the first embodiment. The process for generating the print conditionproperty candidate is continued from a flowchart in FIG. 10 to aflowchart in FIG. 11. Also, the process for generating the printcondition property candidate is a process conducted by the printing WS240 in steps S101 through S106 in FIG. 7.

In step S201 corresponding to a step of receiving an output conditionproperty candidate obtain request, the printing WS 240 receives theprint condition property obtain request. In step S202 corresponding to astep of obtaining an output property, the printing WS 240 generates aproperty candidate necessary to a print execution. In this case, theprint property candidate is generated.

Next, in step S203, the printing WS 240 determines whether or not thereis a Web service client (WSC) to be an edit client (edit C). When thereis no Web service client (WSC), the printing WS 240 advances to stepS214 in FIG. 11. When there is the Web service client (WSC), theprinting WS 240 determines the image editing service candidates in stepS204. In the following step S205, the printing WS 240 substitutes thenumber of the image editing service candidates to a variable X.

Step S206 in FIG. 10 through step S210 in FIG. 11 are looped byevaluating an expression at a top of the loop. When the variable Xbecomes greater than “0” (zero) the loop is terminated.

In step S207 in FIG. 11 in the loop, the edit property candidate obtainrequest is informed to the image editing WS 241 through the Web serviceclient (WSC) 225. In step S208, the printing WS 240 obtains the editproperty candidate from the image editing WS 241 by the edit propertynotice. The variable X is incremented in step S209 and the loop ends instep S210. The loop in steps S207 through S209 is repeated until thevariable X becomes greater than “0” (zero).

When the loop is terminated, the printing WS 240 determines whether ornot the number of the image editing service candidates is greater than“1” in step S211. When the number of the image editing servicecandidates is equal to “1”, the process for generating the printcondition property candidate advances to step S213. When the number ofthe image editing service candidates is greater than “1”, the printingWS 240 merges a plurality of edit properties in step S212 correspondingto a step of merging the edit properties.

After the printing WS 240 merges the plurality of edit properties, theprinting WS 240 merges the print property generated in step S202 and theedit properties so as to generate the print condition property candidatein step S213 corresponding to a step of obtaining the output conditionproperty candidate. Subsequently, the printing WS 240 sends the printcondition property candidate to the client PC 213 in step S214corresponding to a step of providing the output condition propertycandidate, and then terminates the process for obtaining the printcondition property candidate.

By conducting the process for obtaining the print condition propertycandidate, the MFP-A 221 can provide the edit property available by theMFP-B 222 being different from the MFP-A 221 in addition to the editproperty of the MFP-A 221 itself, to the client PC 213.

The sequence flow shown in FIG. 7 describes the process in that theclient PC 213 obtains the print condition property candidate. As a firstprocess for this process, both the print property and the edit propertyare collectively obtained at one time as described above with referenceto the sequence flow in FIG. 7 and the flowcharts in FIG. 10 and FIG.11. Alternatively, as a second process for this process, the printproperty is obtained from the printing WS 240 and the edit property isseparately obtained from the image editing WS 241.

The first process will be described with reference to FIG. 12. FIG. 12is a diagram showing the first process according to the first embodimentof the present invention. In FIG. 12, the client PC 213, the printingservice 210, and the image editing service 211 are shown. In FIG. 12,the print condition property candidate including a print property 402and an edit property 401 is shown between the client PC 213 and theprinting service 210, and the edit property 401 is shown between theprinting service 210 and the image editing service 211.

In a flow of the first process in FIG. 12, first, the client PC 213informs the print condition property candidate obtain request to theprinting service 210 in step S301. In step S302, the printing service210 informs the edit property candidate obtain request to the imageediting service 211. In step S303, the image editing service 211 informsthe edit property 401 to the printing service 210. The printing service210 merges the edit property 401 and the print property 402, and informsthe print condition property candidate to the client PC 213 in stepS304.

In the first process in FIG. 12, a single image editing service 211 isshown. However, in a case in that a plurality of the image editingservices 211 are configured, three methods can be considered as adetermining method for determining which one of image editing services211 is used.

In a first determining method, one of the image editing services 211,which is indicated by the client PC 213 in step S301, is used. In asecond determining method, the image editing services 211 are searchedfor through the network, and one of the image editing services 211 beingsearched is used. In a case of the second determining method, the editproperty, which is indicated by the client PC 213 when a document isprinted out, may be considered to determine the image editing service211 to use. In a third method, the image editing service 211 ispredetermined beforehand to use.

In any one of the above-described determining methods, one or more imageediting services 211 can be determined to use. In a case of determininga plurality of the image editing services 211, the edit propertiesobtained from the plurality of the image editing service 211 are mergedtogether as described in FIG. 11.

Next, various examples of the SOAP messages used in the determiningmethods will be described. FIG. 13 is a diagram showing a SOAP messagein a case in that the client PC indicates the image editing service,according to the first embodiment of the present invention. In FIG. 13,a SOAP message M11 is an example of the SOAP message in the case of thefirst determining method in that the client PC indicates the imageediting service 211. By an XML sentence 410 shown by a tag <m:getPrintCapability> in the SOAP message M11, a URL of the image editing service211 indicates “http://111.222.333.444/editservice”.

FIG. 14 is a diagram showing a SOAP message in a case in that the imageediting service is predetermined beforehand to use, according to thefirst embodiment of the present invention. As shown in FIG. 14, in thiscase of the third determining method in that the image editing service211 is predetermined beforehand to use, a SOAP message M12 omits the URLof the image editing service 211 shown in the SOAP message M11 in FIG.13. Since the image editing service 211 is determined beforehand to use,it is not required to indicate the image editing service 211 to use inthe third determining method.

Next, examples of the print condition property candidate will bedescribed with reference to FIG. 15 and FIG. 16. FIG. 15 is a diagramshowing an example of the print condition property candidate accordingto the first embodiment of the present invention. In FIG. 15, a SOAPmessage M13 for the print condition property candidate shows that theuser can set the number of copies, the size of a sheet and a direction,and can set to paste the confidential stamp and a page stamp.

In detail, an XML sentence 411 shows that the user can set the number ofcopies from 1 to 99 as shown by “1-99”. An XML sentence 412 shows thatthe user can set “A4” or “B4” as the size of a sheet as shown by“A4F/B4F”. An XML sentence 413 shows that the user can set to paste theconfidential stamp or the page stamp as shown by“secret_stamp/page_stamp”.

FIG. 16 is a diagram showing another example the print conditionproperty candidate according to the first embodiment of the presentinvention. A SOAP message M14 for the print condition property candidateshows the same contents as the SOAP message M13 but has a different datastructure from the SOAP message M13 shown in FIG. 15. In detail, an XMLsentence 414 in FIG. 16 corresponds to the XML sentence 411 in FIG. 15,the XML sentence 415 in FIG. 16 corresponds to the XML 412 in FIG. 15,and an XML sentence 416 in FIG. 16 corresponds to the XML sentence 416in FIG. 15.

As described above, since the print condition property candidate isinformed by XML sentences using tags, it is not required to modify theapplication 229 of the client PC 213 even if the print conditionproperty candidate is changed.

Next, the second process will be described with reference to FIG. 17.FIG. 17 is a diagram showing the second process according to the firstembodiment of the present invention. In FIG. 17, the client PC 213, theprinting service 210, the image editing service 211 are shown. In FIG.17, the print property 402, the edit capability 420, and the imageediting service candidate 421 are shown between the client PC 213 andthe printing service 210. The edit property 401 is shown between theclient PC 213 and the image editing service 211.

The edit capability 420 is edit information concerning an edit andinforming that a document can be edited by using the image editingservice 211. Also, the image editing service candidate 421 is optionalinformation to inform the image editing service candidate, for example,by using an URL. In a case in that the image editing service candidate421 is not informed, the client PC 213 is required to inform the imageediting service 211 to use. As described above, information concerning aprovider providing the edit property is sent to the client PC 213.

Next, in a flow of the second process in FIG. 17, in step S401, theclient PC 213 informs the print candidate property candidate obtainrequest to the printing service 210. In step S402, the printing service210 informs the print property 402, the edit capability 420, the imageediting service candidate 421 to the client PC 213.

In step S403, the client PC 213 sends the edit property candidate obtainrequest to the image editing service candidate 421 informed from theprinting service 210 or/and the image editing service 211 searched bythe client PC 213 itself. In step S404, the image editing service 211informs an edit property candidate.

As described above, in the second process, the client PC 213 separatelyobtains the edit property and the print property. A SOAP message sentfrom the client PC 213 to the printing service 210 is the same as theSOAP message shown in FIG. 14. Also, a SOAP message sent from theprinting service 210 to the client PC 213 is the same as the SOAPmessage shown in FIG. 18 or FIG. 19.

FIG. 18 is a diagram showing an example of a SOAP message including theimage editing service candidate according to the first embodiment of thepresent invention. A SOAP message M15 including the image editingservice candidate shown in FIG. 18 shows the print property 402, theedit capability 420, and the image editing service candidate 421. An XMLsentence 426 corresponds to the print property 402. An XML sentence 427corresponds to the edit capability 420 and shows by “true” that the usercan edit a document. An XML sentence 425 corresponds to the imageediting service candidate 421 and shows the URL of the image editingservice candidate 421.

The SOAP message in FIG. 18 shows the image editing service candidate421 by the XML sentence 425. Alternatively, a SOAP message in a case inthat the image editing service candidate 421 is not informed is shown inFIG. 19. FIG. 19 is a diagram showing another SOAP message including theedit capability according to the first embodiment. As shown in FIG. 19,in a SOAP message M16, an XML sentence 426 corresponding to the printproperty 402 and an XML sentence 427 corresponding to the editcapability 420 are shown but the image editing service candidate 421 isnot shown.

When the client PC 213 receives the SOAP messages described above, theclient PC 213 requests the image editing service 211 to send the editproperty 401 and receives the edit property 401 from the image editingservice 211.

After the client PC 213 obtains the edit property 401 and the printproperty 402, the client PC 213 displays a screen 440 as shown in FIG.20. FIG. 20 is a diagram showing a screen to set a print function and anadvanced function, according to the first embodiment of the presentinvention. In FIG. 20, the screen 440 is displayed in the same manner inthe first process and the second process.

The screen 440 will be described. The screen 440 is displayed for theuser to set to use or not functions shown by the print property 402 andthe edit property 401 and for the user to conduct to print out adocument.

The screen 440 displays a print function 430 showing functionsexecutable by obtaining the print property 402, an advanced function 431showing functions executable by obtaining the edit property 401, a printbutton 436 for executing a print, and a cancel button 437 for cancelingthe print.

Moreover, at the print function 430, a setting area 432 for setting thenumber of copies, and a setting area 434 for setting the size of a sheetare displayed. The setting area 432 for setting the number of copies isa text box for the user to set the number of copies as shown in FIG. 20.The setting area 434 for setting the size of sheet is a pull-down menufor the user to select and set the size of a sheet.

Furthermore, at the advanced function 431 displays a setting area 435for setting a confidential stamp. In a case of pasting the confidentialstamp, the user checks a radio button and selects and sets a drawinglocation from the pull-down menu.

After the user sets the print function 430 and the advanced function431, if the user cancels the settings, the user presses the cancelbutton 437. If the user executes a print, the user presses the printbutton 436. When the user presses the print button 436, the client PC213 requests the MFP-A 221 to print out the document. A processconcerning a print after the user presses the print button 436 will bedescribed with reference to FIG. 21 and FIG. 22. FIG. 21 and FIG. 22 arediagrams showing a sequence flow for explaining the process for printinga document according to the first embodiment of the present invention.

In step S107, the client PC 213 sends a document print request to theMFP-A 221. The document print request is conducted by a SOAP message,which will be described later. A document and a print condition createdby selecting from the print condition property candidate by the user areinformed by the document print request. In the process shown in FIG. 21and FIG. 22, as the print condition, the client PC 213 requests to pastethe confidential stamp.

When the document print request is informed to the printing WS 240, theprinting WS 240 conducts a process flow of the printing service, whichwill be described later. The printing WS 240 sends a WS request sendrequest, which requests the Web service client (WSC) 225 to send a WSrequest to the MFP-B 222, to the Web service client (WSC) 225 in stepS108. This WS request send request informs a method name showing adocument edit request, edit contents including a paste of theconfidential stamp, a URL of the image editing WS 241, and a document,to the Web service client (WSC) 225.

In step S109, the Web service client WSC 225 sends the document editrequest to the MFP-B 222. The document edit request is informed by aSOAP message, which will be described later. This SOAP message informsthe document and the edit contents including the paste of theconfidential stamp, which are informed by the WS request send request instep S108.

Subsequently, the process will be described in FIG. 22. In step S110,the image editing WS 241 edits the document and informs an edit resultto the Web service client (WSC) 225 with an edited document to the Webservice client (WSC) 225. The edit result is sent by a SOAP message,which will be described in FIG. 27. Next, in step S111, the Web serviceclient (WSC) 225 sends the edit result with the edited document to theprinting WS 240.

When the printing WS 240 receives the edited document, the printing WS240 prints out the edited document, and informs a document print acceptresult to the client PC 213 in step S112. The document print acceptresult is informed by a SOAP message, which will be described in FIG.28.

The process concerning a print according to the present invention hasbeen described above. Next, the SOAP messages informed in the processconcerning a print and a flowchart of the process will be described.First, the SOAP message informed by the document print request in stepS107 will be described with reference to FIG. 23. FIG. 23 is a diagramshowing an example of a SOAP message informed by the document printrequest according to the first embodiment of the present invention. ASOAP message M17 shown in FIG. 23 includes information concerning adocument name, the number of copies, the size of a sheet, and a stamp.

An XML sentence 450 shows that the document to send has the documentname “content.tiff”. An XML sentence 451 shows three copies. An XMLsentence 452 shows to print out the edited document by horizontal A4. AnXML sentence 453 shows to paste the confidential stamp.

Next, the process conducted by the printing WS 240 in FIG. 21 and FIG.22 will be described with reference to FIG. 24. In step S501, theprinting WS 240 accepts the document print requests. Next, the printingWS 240 determines a presence of an edit indication in step S502. Whenthere is no edit indication, the printing WS 240 advances to step S505.

When there is the edit indication, the printing WS 240 sends thedocument edit request to the image editing WS 241 through the Webservice client (WSC) 225 in step S503. In step S504, the printing WS 240obtains an edit result notice and the edited document from the imageediting WS 241.

In step S505, the printing WS 240 sends a print request for the editeddocument to the ECS 35. In step S506, the printing WS 240 sends thedocument print accept result to the client PC 213 and terminates theprocess.

Next, a function used in step S108 in FIG. 21 will be described withreference to FIG. 25. FIG. 25 is a diagram showing a prototype of thefunction used by in step S108 in FIG. 21, according to the firstembodiment of the present invention. The function shown in FIG. 25 is afunction used in C programming language or C++ language. The functionshown in FIG. 25 has a function name “callWebService” and a return valueof an integer type, and five arguments. These five arguments will bedescribed.

“webServiceURL” is a pointer of a character type and indicates a topaddress where a URL of a Web service is stored in a memory.“webServiceName” indicates a top address where a service name of the Webservice is stored in the memory.

“webServiceMethodName” indicates a top address where the method name isstored in the memory. “argumentList” indicates an address storing a topaddress where method arguments are stored in the memory. “resultList”indicates an address storing a top address where response data arestored in the memory. “error” stores error information.

“webServiceURL”, “webServiceName”, “webServiceMethodName”, and“argumentList” are set at a side using the function, and “resultList”and “error” are set by the function.

Next, the SOAP message to the MFP-B 222 in step S109 in FIG. 21 will bedescribed with reference to FIG. 26. FIG. 26 is a diagram showing a SOAPmessage showing the document edit request according to the firstembodiment of the present invention. A SOAP message M18 shown in FIG. 26shows a document edit request and requests to paste the confidentialstamp by an XML sentence 454.

Next, the SOAP message informed in step S110 in FIG. 22 will bedescribed with reference to FIG. 27. FIG. 27 is a diagram showing a SOAPmessage showing the edit result notice according to the first embodimentof the present invention. A SOAP message M19 shown in FIG. 27 shows theedit result notice, and an XML sentence 455 indicates a file name“content.tiff” of the document in which the confidential stamp ispasted. Actual document data following to the SOAP message M19 are sentto the Web service control 225.

Next, the SOAP message informed in step S112 in FIG. 22 will bedescribed with reference to FIG. 28. FIG. 28 is a diagram showing theSOAP message for the document print accept result according to the firstembodiment of the present invention. The SOAP message M20 shown in FIG.28 shows the document print accept result, and includes a job ID“0987654321” as shown by an XML sentence 456.

In the first embodiment described above, the document subject to edit orprint out is in the client PC 213. Next, in a second embodiment, thedocument is stored in the client PC 213 similar to the first embodiment.However, different from the first embodiment, the document managementservice 212 as a Web service managing the document is implemented in theclient PC 213.

Second Embodiment

A system configuration according to the second embodiment will bedescribed with reference to FIG. 29. FIG. 29 is a diagram showing thesystem configuration according to the second embodiment of the presentinvention. In FIG. 29, a client PC 213, a printing service 210, an imageediting service 211, and a document management service 212, a documentDB 214, and documents 301 and 302 are shown.

As shown in FIG. 29, different from the first embodiment, the number ofdocument transmissions (sending and receiving the document) is reducedto two times (see FIG. 5). By reducing the number of the documenttransmissions, it is possible to reduce the number of chances ofattacking the documents 301 and 302 such as interception andfalsification.

In a flow of the document transmission, the document 301 is sent fromthe document management service 212 of the client PC 213 to the imageediting service 211, and is edited by the image editing service 211.Then, an edited document (document 301) is sent from the image editingservice 211 to the printing service 210, and is printed out by theprinting service 210.

As described above, the second embodiment is different from the firstembodiment in that the document 301 is directly sent from the client PC213 to the image editing service 211.

Next, a functional configuration according to the second embodiment willbe described with reference to FIG. 30 in detail. FIG. 30 is a diagramshowing the functional configuration according to the second embodimentof the present invention. In FIG. 30, the client PC 213, the MFP-A 211,and the MFP-B 222 are shown. Referring to FIG. 30, parts different fromthe first embodiment (see FIG. 6) will be described. First, the clientPC 213 includes a repository Web service 231 as the document managementservice 212, and a Web service server engine 232. The Web service serverengine 232 is an engine to execute a server function of the Webservices.

Moreover, in the MFP-B 222, the Web service client (WSC) 225, which isnot used in the first embodiment, is used to function as a client of therepository Web service 231.

The system configuration and the functional configuration according tothe second embodiment are described above. Next, a sequence flow forobtaining the print condition property candidate will be described withreference to FIG. 31. FIG. 31 is a diagram showing the sequence flow ofthe process for obtaining the print condition property candidateaccording to the second embodiment of the present invention. In thesequence flow in FIG. 31, a sequential process, which is conducted amongthe client PC 213, the MFP-A 221, and the MFP-B 222, are shown. In FIG.31, the printing WS 240 collectively represents the Web service server(WSS) 224 and the printing WSF 226 in the MFP-A 221 in FIG. 30. Also,the image editing WS 241 collectively represents the Web service server(WSS) 224 and the image editing WSF 227 in the MFP-B 222 in FIG. 30.

In addition, the sequential process in the sequence flow shown in FIG.31 is a process for obtaining a print condition property candidate.

The sequence flow will be described. In step S601, the client PC 213informs a print condition property candidate obtain request, which is anobtain request for obtaining the print condition property candidate, tothe printing WS 240. In step S602, the printing WS 240 informs a WSrequest send request, which requests sending a WS request to anindicated Web service, to the Web service client (WSC) 225. In thiscase, a URL (Uniform Resource Locater) of the image editing WS 241, anda method name showing an edit property candidate obtain request areinformed with the WS request send request.

In step S603, the Web service client (WSC) 225 informs the edit propertycandidate obtain request to the image editing WS 241 by a SOAP message.In step S604, in response to this SOAP message, the image editing WS 241informs an edit property notice to the Web service client (WSC) 225 bythe SOAP message. By sending the edit property notice, the edit propertyis informed to the MFP-A 221.

In step S605, the Web service client (WSC) 225 informs a WS requestresult notice to the printing WS 240. In this case, the edit propertycandidate informed from the MFP-B 222 is also informed to the printingWS 240. When the edit property candidate is informed to the printing WS240, the printing WS 240 generates the print condition propertycandidate from the print property candidate held by the printing WS 240and the edit property candidate informed from the MFP-B 222. Thisprocess conducted by the printing WS 240 is the same as the processdescribed in accordance with the flowcharts shown in FIG. 10 and FIG.11.

In step S606, after the printing WS 240 generates the print conditionproperty candidate, the printing WS 240 informs the print conditionproperty candidate by the SOAP message.

By the above-described processes, the client PC 213 can obtain the printcondition property candidate.

Next, a process concerning a print according to the second embodimentwill be described with reference to FIG. 32 and FIG. 33. FIG. 32 andFIG. 33 are diagrams showing a sequence flow of the process concerning aprint according to the second embodiment of the present invention. InFIG. 32, in step S607, the application 229 of the client PC 213 informsa document ticket create request to the repository WS 235 in the sameclient PC 213 with an array of document IDs. In step S608, therepository WS 235 sends a response with respect to the document ticketcreate request to the application 229 with a document ticket. In thiscase, the document ID uniquely indicates a document. The document ticketshows permission to edit or print out the document, and is required toedit or print out the document specified by the document ID.

In step S609, the client PC 213 informs a document print request to theMFP-A 221. The document print request is informed by a SOAP message,which will be described later, and the document ticket and the printcondition will be informed with the document print request. In this casein FIG. 31, the client PC 213 requests pasting a confidential stamp as aprint condition property.

When the document print request is informed to the printing WS 240, theprinting WS 240 executes a process flow of the printing servicedescribed in FIG. 24. The printing WS 240 sends a WS request sendrequest, which requests the Web service client (WSC) 225 to send the WSrequest to the MFP-B 222, to the Web service client (WSC) 225 in stepS610. This WS request send request informs a method name showing adocument edit request, edit contents including a paste of theconfidential, a URL of the image editing WS 241, and the documentticket, to the Web service client (WSC) 255, by using the function shownin FIG. 25.

In step S611, the Web service client (WSC) 225 sends the document editrequest to the MFP-B 222. A SOAP message for the document edit requestis the same as the SOAP message M18 shown in FIG. 26. Also, the documentticket and the edit contents showing to paste the confidential stamp,which are previously informed, are informed by this SOAP message.

Next, in step S612, the image editing WS 241 sends the WS request sendrequest to the Web service client (WSC) 225 in the MFP-B 222 to get back(retrieve) the document from the repository WS 235. The function shownin FIG. 25 is used for this WS request send request, and a URL of therepository WS 235, a method showing a document get back request, and thedocument ticket are informed to the Web service client (WSC) 225.

In step S613, the Web service client (WSC) 225 sends the document getback request to the repository WS 235 with the document ticket. Theprocess concerning a print is continued to the sequence flow shown inFIG. 33. Instep S614, the repository WS 235 sends a response withrespect to the document get back request. In this case, the document isreturned to the MFP-B 222. When the Web service client (WSC) 225 getsback the document, the Web service client (WSC) 225 sends a responseincluding a request result with the document to the image editing WS 241in step S615.

In step S616, the image editing WS 241 edits the document and sends anedit result with the edited document to the Web service client (WSC) 225of the MFP-A 221. The edit result is sent by the SOAP message M19 shownin FIG. 27. Next, in step S617, the Web service client (WSC) 225 sendsthe edit result with the edited document to the printing WS 240.

When the edited document is sent to the printing WS 240, the printing WS240 prints out the document and sends a document print accept result tothe client PC 213 in step S618. The document print accept result is sentby the SOAP message M20 described in FIG. 28.

Next, a SOAP message sent from the application 229 to the printing WS240 in step S609 will be described with reference to FIG. 34. The SOAPmessage shown M21 in FIG. 34 is a SOAP message for the document printrequest, but is different from the SOAP message M17 shown in FIG. 23 inthe first embodiment and instead of the document name, the documentticket is indicated by an XML sentence 459. “jfowfnofjofi” is thedocument ticket shown by the XML sentence 459. The SOAP message M21shown in FIG. 34 will be used in the following embodiments until aneighth embodiment.

Next, a third embodiment will be described. In the third embodiment,different from the second embodiment, the document management service212 is separately provided from the client PC 213.

Third Embodiment

FIG. 35 is a block diagram showing a system configuration according tothe third embodiment of the present invention. In FIG. 35, a client PC213, a printing service 210, an image editing service 211, a documentmanagement service 211, a document DB 214, and documents 301 and 302 areshown.

In a flow of the documents 301 and 302 in FIG. 35, the document 302 issent from the document management service 212 to the image editingservice 211, and edited by the image editing service 211. Then, theedited document as the document 301 is sent from the image editingservice 211 to the printing service 210, and prints out the document301.

A functional configuration according to the third embodiment will bedescribed with reference to FIG. 36 in detail. FIG. 36 is a blockdiagram showing the functional configuration according to the thirdembodiment of the present invention. In FIG. 36, the client PC 213, theMFP-A 221, the MFP-B 222, and a MFP-C 233 are shown. In FIG. 36, partsdifferent from the second embodiment will be described. First, theclient PC 213 includes the application 229 and the network interface230, and has the same functional configuration as the first embodiment.

Moreover, the MFP-C 233 is additionally provided as a repositoryservice. The MFP-C 233 includes the NCS 31 having the httpd 223, the Webservice server (WSS) 224, the Web service client (WSC) 225, a repositoryWeb service function (WSF) 234, the MCS 36, and the HDD 65.

The repository WSF 234 is a Web service function (WSF) for providing adocument management function. The MCS 36 is used when the repository WSF234 accesses the HDD 65. The HDD 65 stores the document. It should benoted that the Web service client (WSC) 225 provided in the MFP-B 222 isnot used in the third embodiment.

The above-described system configuration and the functionalconfiguration are implemented in the third embodiment. Next, a processconcerning a print will be described with reference to FIG. 37 and FIG.38. FIG. 37 and FIG. 38 are diagrams showing a sequence flow of theprocess concerning a print, according to the third embodiment of thepresent invention. In the sequence flow shown in FIG. 37 and FIG. 38,the process conducted among the client PC 213, the MFP-A 221, the MFP-B222, and the MFP-C 233 is shown. In FIG. 37 and FIG. 38, the repositoryWS 235 collectively represents the Web service server (WSS) 224 in theMFP-C 233 and the repository WSF 234.

The process shown in FIG. 37 and FIG. 38 is a process in that the clientPC 213 obtains a document ticket and prints out the document.

In step S701, the application 229 of the client PC 123 sends a documentticket create request with an array of document IDs to the repository WS235. The repository WS 235 creates the document ticket, and sends aresponse with respect to the document ticket create request with thedocument ticket, to the client PC 213 in step S702. SOAP messages usedin step S701 and step S702 will be described later with reference toFIG. 39 and FIG. 40.

In step S703, the client PC 213 sends a document print request to theMFP-A 221. The document print request is sent by the SOAP messagedescribed in FIG. 34, and the document ticket, the document, the printcondition property are informed to the printing WS 240 of the MFP-A 221.In this case in FIG. 37, the client PC 213 request pasting aconfidential stamp as the print condition property.

When the document print request is informed to the printing WS 240, theprinting WS 240 executes the process flow of the printing servicedescribed in FIG. 24. The printing WS 240 sends a WS request sendrequest, which requests sending a WS request to an indicated Webservice, to the Web service client (WSC) 225 in step S704. The functionshown in FIG. 25 is used for the WS request send request, and a methodname showing a document edit request, edit contents showing a paste ofthe confidential stamp, a URL of the image editing WS 241, and thedocument ticket are informed to the Web service client (WSC) 225.

In step S705, the Web service client (WSC) 225 sends the document editrequest to the MFP-B 222. A SOAP message for the document edit requestis the same as the SOAP message M18 shown in FIG. 26. The SOAP messageM18 informs the document ticket, and the edit contents showing the pasteof the confidential stamp.

Next, the image editing WS 241 sends a WS request send request to theWeb service client (WSC) 225 to get back (retrieve) the document fromthe repository WS 235 in step S706. The function shown in FIG. 25 isused for the WS request send request, and a URL of the repository WS235, a method name showing a document get back request, and the documentticket are informed to the Web service client (WSC) 225.

Referring to FIG. 38, the Web service client (WSC) 225 sends thedocument get back request with the document ticket to the repository WS235 in step S707. In step S708, the repository WS 235 sends a responsewith respect to the document get back request. In this case, thedocument is returned to the MFP-B 222. When the Web service client (WSC)225 receives the document, the Web service client (WSC) 225 sends aresponse including a request result with the document to the imageediting WS 241 in step S709.

The image editing WS 241 edits the document, and sends an edit resultnotice showing an edit result with the edited document to the Webservice client (WSC) 225 of the MFP-A 221 in step S710. A SOAP messagefor the edit result notice is the same as the SOAP message M19 shown inFIG. 27. Next, the Web service client (WSC) 225 sends the edit resultnotice showing the edit result with the edited document to the printingWS 240 in step S711.

When the printing WS 240 receives the edited document, the printing WS240 prints out the edited document, sends a document print accept resultto the client PC 213 in step S712. A SOAP message for the document printaccept result is the same as the SOAP message M20 shown in FIG. 28.

Next, a SOAP message informed in step S701 in FIG. 37 will be describedwith reference to FIG. 39. FIG. 39 is a diagram showing a SOAP messagefor the document ticket create request according to the third embodimentof the present invention. A SOAP message M22 shown in FIG. 39 shows twodocument IDs “1111” and “1112” as shown by an XML sentence 457. Thedocument ticket is created based on these two document IDs.

A SOAP message for the response with respect to the document ticketcreate request will be described with reference to FIG. 40. FIG. 40 is adiagram showing the SOAP message for the response with respect to thedocument ticket create request according to the third embodiment of thepresent invention. In the SOAP message M23 shown in FIG. 40, theresponse with respect to the document ticket create request includes thedocument ticket “jfowfnofjofi” as shown by an XML sentence 458.

Next, a fourth embodiment will be described. In the fourth embodiment,different from the third embodiment, the document transmission (sendingand receiving a document) is conducted between the document managementservice 212 and the printing service 210.

Fourth Embodiment

FIG. 41 is a block diagram showing a system configuration according tothe fourth embodiment of the present invention. In FIG. 41, a he clientPC 213, a printing service 210, an image editing service 211, a documentmanagement service 212, a document DB 214, and documents 301, 302, and303 are shown.

In a document flow in FIG. 41, the document 301 is sent from thedocument management service 212 to the printing service 210, and is sentfrom the printing service 210 to the image editing service 211 as thedocument 302. The document 302 edited by the image editing service 211is sent to the printing service 210 as the document 303, and is printedout from the printing service 210.

Next, a functional configuration will be described with reference toFIG. 42 in detail. FIG. 42 is a block diagram showing the functionalconfiguration according to the fourth embodiment of the presentinvention. In FIG. 42, the client PC 213, the MFP-A 221, the MFP-B 222,and the MFP-C 233 are shown. In FIG. 42, parts different from the thirdembodiment will be described. In the fourth embodiment, different fromthe third embodiment, the Web service client (WSC) 225 is not requiredsince the MFP-B 222 is not required to be a client of the Web service.

The system configuration and the functional configuration are describedabove. Next, a process concerning a print will be described inaccordance with a sequence flow with respect to FIG. 43 and FIG. 44.FIG. 43 and FIG. 44 are diagrams showing a sequence flow of the processconcerning a print according to the fourth embodiment of the presentinvention. In the sequence flow shown in FIG. 43 and FIG. 44, theprocess is conducted among the client PC 213, the MFP-A 221, the MFP-B222, and the MFP-C 233.

Also, in the process in accordance with the sequence flow shown in FIG.43 and FIG. 44, the client PC 213 obtains a document ticket, and printsout a document specified by the document ticket.

In step S801, the application 229 of the client PC 213 sends a documentticket create request with an array of document IDs to the repository WS235. The repository 235 creates a document ticket, and sends a responsewith the document ticket with respect to the document ticket createrequest in step S802. SOAP messages used in step S801 and step S802 arethe same as the SOAP messages M22 and M23 described with reference toFIG. 39 and FIG. 40.

In step S803, the client PC 213 sends a document print request to theMFP-A 221. In this case, the SOAP message M21 described in FIG. 34 isused, and the document ticket, the document, and the print conditionproperty are informed. In a case in FIG. 43, the client PC 213 requestspasting the confidential stamp as the print condition property.

When the document print request is informed to the printing WS 240, theprinting WS 240 executes the process flow of the printing servicedescribed in FIG. 24. In step S804, the printing WS 240 sends a WSrequest send request with respect to the Web service client (WSC) 225.The function shown in FIG. 25 is used for the WS request send request,and a method name showing a document get back request, a URL of therepository WS 235, and the document ticket are informed to the Webservice client (WSC) 225.

In step S805, the Web service client (WSC) 225 sends the document getback request to the repository WS 235. A SOAP message for the documentget back request informs the document ticket. In step S806, therepository WS 235 sends a response including the document to the Webservice client (WSC) 225. When the Web service client (WSC) 225 receivesthe document, the Web service client (WSC) 225 sends a responseincluding a request result with the document to the image editing WS 241in step S807.

Referring to FIG. 44, in step S808, the printing WS 240 sends a WSrequest send request to the Web service client (WSC) 225. The functionshown in FIG. 25 is used for the WS request send request, and a URL ofthe image editing WS 241 and the document are informed to the Webservice client (WSC) 225.

In step S809, the Web service client (WSC) 225 sends the document editrequest to the MFP-B 222. A SOAP message for the document edit requestinforms the document, and the edit contents showing to paste theconfidential stamp.

The image editing WS 241 edits the document, and sends an edit resultnotice including an edit result with the edited document to the Webservice client (WSC) 225 in step S810. A SOAP message M19 shown in FIG.27 is used for the edit result notice. Next, in step S811, the Webservice client (WSC) 225 sends the edit result notice including an editresult with the edited document to the printing WS 240.

When the printing WS 240 receives the edited document, the printing WS240 prints out the document, and sends a document print accept result tothe client PC 213 in step S812. A SOAP message for the document printaccept result is the same as the SOAP message M20 described in FIG. 28.

The fourth embodiment is described above. Next, a fifth embodiment willbe described. In the fifth embodiment, the document management service212 and the printing service 210 are implemented in a single MFP as themulti-functional apparatus 1.

Fifth Embodiment

FIG. 45 is a diagram showing a system configuration according to thefifth embodiment of the present invention. In FIG. 45, a client PC 213,a printing service 210, a document management service 212, an imageediting service 211, a document DB 214, and a documents 301 and 302 areshown.

In a document flow in FIG. 45, the document 301 is sent from thedocument management service 212 to the image editing service 211. Thedocument 302, which is edited by the image editing service 211, is sentto the printing service 210, and printed out from the printing service210.

Next, a functional configuration will be described with reference toFIG. 46 in detail. FIG. 46 is a block diagram showing the functionalconfiguration according to the fifth embodiment of the presentinvention. In FIG. 46, the client PC 213, the MFP-A 221, and the MFP-B222 are shown. The image editing service 211 is implemented in the MFP-B222.

The system configuration and the functional configuration in the fifthembodiment are described above. Next, a process for obtaining a printcondition property candidate will be described in accordance with asequence flow with reference to FIG. 47, and a process concerning aprint will be described in accordance with a sequence flow withreference to FIG. 48 and FIG. 49. FIG. 47 is a diagram showing thesequence flow of the process for obtaining a print condition propertyaccording to the fifth embodiment of the present invention. FIG. 48 andFIG. 49 are diagrams showing the sequence flow of the process concerninga print according to the fifth embodiment of the present invention. InFIG. 47, FIG. 48, and FIG. 49, the processes among the client PC 213,the MFP-A 221, and the MFP-B 222 are shown. In FIG. 47, FIG. 48, andFIG. 49, the printing WS 240 collectively represents the Web serviceserver (WSS) 224 in the MFP-A 221 and the printing WSF 226 in FIG. 46.Similarly, the repository WS 235 collectively represents the Web serviceserver (WSS) 224 in the MFP-A 221 and the repository WSF 234 in FIG. 46.

The process for obtaining the print condition property candidate shownin FIG. 47 is a process in that the client PC 213 obtains the printcondition property candidate. The process concerning the print shown inFIG. 48 and FIG. 49 is a process in that the client PC 213 obtains adocument ticket and prints out the document.

The sequence flow in FIG. 47 will be described. In step S901, the clientPC 213 sends a print condition property candidate obtain request, whichis an obtain request for obtaining the print condition propertycandidate, to the printing WS 240. In step S902, the printing WS 240sends a WS request send request, which requests sending a WS request toan indicated Web service, to the Web service client (WSC) 225. In thiscase, a URL of the image editing WS and a method name showing an editproperty candidate obtain request are informed with the WS request sendrequest.

In step S903, the Web service client (WSC) 225 sends the edit propertycandidate obtain request to the image editing WS 241 by a SOAP message.In response to the edit property candidate obtain request, the imageediting WS 241 sends an edit property notice to the Web service client(WSC) 225 by a SOAP message in step S904. Accordingly, the edit propertyis informed to the MFP-A 221.

In step S905, the Web service client (WSC) 225 sends a WS request resultnotice to the printing WS 240. In this case, the edit property candidateinformed from the MFP-B 222 is also informed to the printing WS 240.When the printing WS 240 receives the edit property candidate, theprinting WS 240 generates a print condition property candidate from theprint property candidate possessed in the printing WS 240 itself and theedit property candidate. This process is the same as the processdescribed in accordance with the flowchart in FIG. 11.

After the printing WS 240 generates the print condition propertycandidate, the printing WS 240 sends the print condition propertycandidate to the client PC 213 by a SOAP message in step S906.

Accordingly, the client PC 213 can obtain the print condition propertycandidate.

Next, the process concerning the print will be described in accordancewith the sequence flow shown in FIG. 48 and FIG. 49. In step S907, theclient PC 213 sends a document ticket create request with an array ofdocument IDs to the repository WS 235. In step S908, the repository WS235 sends a response with respect to the document ticket request withthe document ticket to the client PC 213.

In step S909, the client PC 213 sends a document print request to theMFP-A 221. The document print request is sent by the SOAP message M21 inFIG. 34, and the document ticket and the print condition are informed.In a case in FIG. 48, the client PC 213 requests to paste theconfidential stamp as the print condition property.

When the printing WS 240 receives the document print request, theprinting WS 240 executes the process flow of the printing servicedescribed in FIG. 24. The printing WS 240 sends a WS request sendrequest to the Web service client (WSC) 225 in step S910. The functionshown in FIG. 25 is used for the WS request send request, and a methodname showing the document edit request, edit contents indicating topaste the confidential stamp, a URL of the image editing WS 241, and thedocument ticket are informed to the Web service client (WSC) 225.

In step S911, the Web service client (WSC) 225 sends a document editrequest to the MFP-B 222. A SOAP message for the document edit requestis the same as the SOAP message M18 shown in FIG. 26. Also, the documentticket and the edit contents are informed by the SOAP message M18.

Next, in step S912, the image editing WS 241 sends a WS request sendrequest to the Web service client (WSC) 225 in the MFP-B 222 to get back(retrieve) the document from the repository WS 235. The function shownin FIG. 25 is used for the WS request send request, and a URL of therepository WS 235, a method name showing a document get back request,and the document ticket are informed to the Web service client (WSC)225.

In step S913, the Web service client (WSC) 225 sends the document getback request with the document ticket to the repository WS 235.Subsequently, the sequence flow in FIG. 49 will be described. In step S914, the repository WS 235 sends a response with respect to the documentget back request to the Web service client (WSC) 225 of the MFP-B 222.In this case, the MFP-B 222 gets back the document from the repositoryWS 235. When the Web service client (WSC) 225 of the MFP-B 222 receivesthe document, the Web service client (WSC) 225 sends a responseincluding a request result with the document to the image editing WS 241in step S915.

The image editing WS 241 edits the document, and sends an edit resultnotice showing the edit result with the edited document to the Webservice client (WSC) 225 of the MFP-A 221 in step S916. A SOAP message,which is the same as the SOAP message M19 shown in FIG. 27, is used forthe edit result notice. Next, the Web service client (WSC) 225 sends theedit result notice showing the edit result with the edited document tothe printing WS 240 in step S917.

When the printing WS 240 receives the edited document, the printing WS240 prints out the document, and sends a document print accept result tothe client PC 213 in step S918. The document print accept result is sentby the SOAP message M20 described in FIG. 28.

The fifth embodiment is described above. Next, a sixth embodiment willbe described. In the sixth embodiment, the document management service212 and the image editing service 211 are implemented in a single MFP asthe multi-functional apparatus 1.

Sixth Embodiment

FIG. 50 is a block diagram showing a system configuration according tothe sixth embodiment of the present invention. In FIG. 50, a client PC213, a printing service 210, a document management service 212, an imageediting service 211, a document DB 214, and document 301.

In a document flow in FIG. 50, the document 301 is sent from the imageediting service 211 to the printing service 210, and is printed out fromthe printing service 210. Accordingly, the document transmission isconducted just once.

Next, a functional configuration will be described with reference toFIG. 51 in detail. In FIG. 51, the client PC 213, the MFP-A 221, and theMFP-B 222 are shown. In FIG. 51, the image editing WSF 227 and therepository WSF 234 are implemented in the MFP-B 222. Accordingly, theprinting WSF 226 is implemented in the MFP-A 221.

The system configuration and the functional configuration in the sixthembodiment are described above. Next, a process for obtaining a printcondition property candidate and a process concerning a print will bedescribed in accordance with sequence flows. In the sequence flows shownin FIG. 52, FIG. 53, and FIG. 54, processes, which are conducted amongthe client PC 213, the MFP-A 221, and the MFP-B 222, are shown. In FIG.52, FIG. 53, and FIG. 54, the image editing WS 241 collectivelyrepresents the Web service server (WSS) 224 and the image editing WSF227 in FIG. 51. Similarly, the repository WS 235 collectively representsthe Web service server (WSS) 224 and the repository WSF 234 in FIG. 51.

In the process shown in FIG. 52, the client PC 213 obtains the printcondition property candidate. In the process shown in FIG. 53 and FIG.54, the client PC 213 obtains a document ticket and prints out thedocument.

The sequence flow for obtaining the print condition property candidatewill be described with reference to FIG. 52. FIG. 52 is a diagramshowing the sequence flow of the process for obtaining the printcondition property candidate according to the sixth embodiment of thepresent invention. In FIG. 52, in step S1001, the client PC 213 sends aprint condition property candidate obtain request to the printing WS240. In step S1002, the printing WS 240 sends a WS request send requestto the Web service client (WSC) 225 in the MFP-A 221. In this case, aURL of the image editing WS 241 and a method name showing the editproperty candidate obtain request are informed to the Web service client(WSC) 225 of the MFP-A 221.

In step S1003, the Web service client of the MFP-A 221 sends an editproperty candidate obtain request to the image editing WS 241 by a SOAPmessage. In step S1004, in response to the edit property candidateobtain request, the image editing WS 241 sends an edit property noticeto the Web service client (WSC) 225 of the MFP-A 221. Accordingly, theedit property is informed to the MFP-A 221.

In step S1005, the Web service client (WSC) 225 of the MFP-A 221 sends aWS request result notice to the printing WS 240. In this case, the editproperty candidate, which is informed from the MFP-B 222, is alsoinformed to the printing WS 240. When the printing WS 240 receives theedit property candidate, the printing WS 240 generates the printcondition property candidate from the print property candidate possessedin the printing WS 240 itself and the edit property candidate informedfrom the Web service client (WSC) 225. This process is the same as theprocess described in accordance with the flowchart shown in FIG. 11.

After the printing WS 240 generates the print condition propertycandidate, the printing WS 240 sends the print condition propertycandidate to the client PC 213 by a SOAP message in step S1006.

By the above-described process, the client PC 213 can obtain the printcondition property candidate.

Next, the process concerning the print will be described with referenceto FIG. 53 and FIG. 54. In step S1007, the client PC 213 sends adocument ticket create request with an array of document IDs to therepository WS 235. In step S1008, the repository WS 235 sends a responsewith a document ticket with respect to the document ticket createrequest to the client PC 213.

In step S1009, the client PC 213 sends a document print request to theMFP-A 221. The document print request is sent by the SOAP message M21shown in FIG. 34, and the document ticket and the print condition areinformed to the MFP-A 221. In a case in FIG. 53, the client PC 213requests to paste the confidential stamp as the print conditionproperty.

When the printing WS 240 receives the document print request, theprinting WS 240 executes the process flow of the printing servicedescribed in FIG. 24. The printing WS 240 sends a WS request sendrequest to the Web service client (WSC) 225 of the MFP-A 221 in stepS1010. The function shown in FIG. 25 is used for the WS request sendrequest, and a method name showing the document edit request, editcontents indicating to paste the confidential stamp, a URL of the imageediting WS 241, and the document ticket are informed to the Web serviceclient (WSC) 225 of the MFP-A 221.

In step S1011, the WSC 225 of the MFP-A 221 sends the document editrequest to the MFP-B 222. A SOAP message for the document edit requestis the same as the SOAP message M18 shown in FIG. 26, and the documentticket and the edit contents are informed by the SOAP message.

Next, in step S1012, the image editing WS 241 sends a document get backrequest with the document ticket to the repository WS 235 in the MFP-B222 in order to get back (retrieve) the document from the repository WS235.

Subsequently, referring to FIG. 54, in step S1013, the repository WS 235sends a response including a request result and the document to theimage editing WS 241.

The image editing WS 241 edits the document, and sends an edit resultwith the edited document to the Web service client (WSC) 225 of theMFP-A 221 in step S1014. The edit result is sent by the SOAP message M19shown in FIG. 27. Next, in step S1015, the Web service client (WSC) 225sends the edit result with the edited document to the printing WS 240.

When the printing WS 240 receives the edited document, the printing WS240 prints out the edited document and sends a document print acceptresult to the client PC 213 in step S1016. The document print acceptresult is sent by the SOAP message M20 described in FIG. 28.

The sixth embodiment is described above. Next, a seventh embodiment willbe described. In the seventh embodiment, the printing service 210 andthe image editing service 211 are implemented in a single MFP as themulti-functional apparatus 1.

Seventh Embodiment

FIG. 55 is a block diagram showing a system configuration according tothe seventh embodiment of the present invention. In FIG. 55, a client PC213, a printing service 210, a document management service 212, an imageediting service 211, a document DB 214, and a document 301 are shown.

In a document flow in FIG. 55, the document 301 is sent from thedocument management service 212 to the image editing service 211, and anedited document as the document 301 is printed out from the printingservice 210. Accordingly, the document transmission is conducted justonce.

Next, a functional configuration will be described with reference toFIG. 56 in detail. In FIG. 56, the client PC 213, the MFP-A 221, and theMFP-B 222 are shown. In FIG. 56, the printing WSF 226 as the printingservice 210 and the image editing WSF 227 as the image editing service211 are implemented in the MFP-A 221. Moreover, the repository WSF 234as the repository service is implemented in the MFP-B 222.

The system configuration and the functional configuration in seventhembodiment are described above. Next, a process for obtaining a printcondition property candidate and a process concerning a print will bedescribed in accordance with sequence flows. In the sequence flows shownin FIG. 57, FIG. 58, and FIG. 59, processes, which are conducted amongthe client PC 213, the MFP-A 221, and the MFP-B 222, are shown. In FIG.57, FIG. 58, and FIG. 59, the printing WS 240 collectively representsthe Web service server (WSS) 224 and the printing WSF 226 in the MFP-A221 in FIG. 56. Similarly, the image editing WS 241 collectivelyrepresents the Web service server (WSS) 224 and the image editing WSF227 in the MFP-A 221 in FIG. 56.

In the process shown in FIG. 57, the client PC 213 obtains the printcondition property candidate. In the process shown in FIG. 58 and FIG.59, the client PC 213 obtains a document ticket and prints out thedocument.

The sequence flow for obtaining the print condition property candidatewill be described with reference to FIG. 57. FIG. 52 is a diagramshowing the sequence flow of the process for obtaining the printcondition property candidate according to the seventh embodiment of thepresent invention. In FIG. 57, in step S1101, the client PC 213 sends aprint condition property candidate obtain request to the printing WS240. In step S1102, the printing WS 240 sends a WS request send requestto the image editing WS 241. In response to the WS request send request,the image editing WS 241 informs an edit property notice to the printingWS 240 in step S1103.

When the printing WS 240 receives the edit property candidate, theprinting WS 240 generates the print condition property candidate fromthe print property possessed in the printing WS 240 itself and the editproperty candidate informed from the image editing WS 241. This processis conducted as described in accordance with the flowchart shown in FIG.11.

After the printing WS 240 generates the print condition propertycandidate, the printing WS 240 sends the print condition propertycandidate by a SOAP message to the client PC 213 in step S1104.

By the above-described process, the client PC 213 can obtain the printcondition property candidate.

Next, the process concerning the print will be described with referenceto FIG. 58 and FIG. 59. In step S1105, the client PC 213 sends adocument ticket create request with an array of document IDs to therepository WS 235. In step S1106, the repository WS 235 sends a responsewith a document ticket with respect to the document ticket createrequest to the client PC 213.

In step S1107, the client PC 213 sends a document print request to theMFP-A 221. The document print request is sent by the SOAP message M21shown in FIG. 34, and the document ticket and the print condition areinformed to the MFP-A 221. In a case in FIG. 58, the client PC 213requests to paste the confidential stamp as the print conditionproperty.

When the printing WS 240 receives the document print request, theprinting WS 240 executes the process flow of the printing servicedescribed in FIG. 24. In step S1108, the printing WS 240 sends adocument edit request to the image editing WS 241. The document editrequest informs the document ticket and the edit contents.

Next, in step S1109, the image editing WS 241 sends a WS request sendrequest to the Web service client (WSC) 225 in order to get back(retrieve) the document from the repository WS 235. The function shownin FIG. 25 is used for the WS request send request, and a URL of therepository WS 235, a method name showing a document get back request,and the document ticket to the Web service client (WSC) 225 of the MFP-A221. The Web service client (WSC) 225 sends the document get backrequest with the document ticket to the repository WS 235 (step S1110).

Subsequently, referring to FIG. 54, in step S1111, the repository WS 235sends a response including a request result and the document withrespect the document get back request. In this case, the document isreturned to the MFP-A 221. When the Web service client (WSC) 225receives the document, the Web service client (WSC) 225 sends a responseincluding a request result and the document in step S1112.

The image editing WS 241 edits the document, and sends an edit resultnotice showing an edit result with the edited document to the printingWS 240 in step S1113. When the printing WS 240 receives the editeddocument, the printing WS 240 prints out the edited document, and sendsa document print accept result to the client PC 213 in step S1114. Thedocument print accept result is sent by the SOAP message M20 describedin FIG. 28.

The seventh embodiment is described above. Next, an eighth embodimentwill be described. In the eighth embodiment, all three services: aprinting service 210, a document management service 212, and an imageediting service 211, are implemented in a single MFP as themulti-functional apparatus 1.

Eighth Embodiment

FIG. 60 is a block diagram showing a system configuration according tothe eighth embodiment of the present invention. In FIG. 60, the clientPC 213, the printing service 210, the document management service 212,the image editing service 211, the document DB 214, and the document 301are shown.

In a document flow in FIG. 60, since the document is stored in an MFPthat edits and/or prints out the document, the document transmission isnot conducted.

Next, a functional configuration will be described with reference toFIG. 61 in detail. In FIG. 61, the client PC 213 and the MFP-A 221 areshown. In FIG. 61, the printing WSF 226 as the printing service 210, theimage editing WSF 227 as the image edit service 211, and the repositoryWSF 234 as the document management service 212 are implemented in theMFP-A 221.

The system configuration and the functional configuration in eighthembodiment are described above. a process for obtaining a printcondition property candidate and a process concerning a print will bedescribed in accordance with sequence flows. In the sequence flows shownin FIG. 62, FIG. 63, and FIG. 64, processes, which are conducted amongthe client PC 213, and the MFP-A 221, are shown. In FIG. 62, FIG. 63,and FIG. 64, the image editing WS 241 collectively represents the Webservice server (WSS) 224 and the image editing WSF 227 in the MFP-A 221in FIG. 61. Similarly, the repository WS 235 collectively represents theWeb service server (WSS) 224 and the repository WSF 234 in FIG. 61.Moreover, the printing WS 240 collectively represents the Web serviceserver (WSS) 224 and the printing WSF 226 in the MFP-A 221 in FIG. 61.

In the process shown in FIG. 62, the client PC 213 obtains the printcondition property candidate. In the process shown in FIG. 63 and FIG.64, the client PC 213 obtains a document ticket and prints out thedocument.

The sequence flow for obtaining the print condition property candidatewill be described with reference to FIG. 62. FIG. 62 is a diagramshowing the sequence flow of the process for obtaining the printcondition property candidate according to the eighth embodiment of thepresent invention. In FIG. 62, in step S1201, the client PC 213 sends aprint condition property candidate obtain request to the printing WS240. In step S1102, the printing WS 240 sends an edit property candidateobtain request to the image editing WS 241. In response to the editproperty candidate obtain request, the image editing WS 241 informs anedit property notice to the printing WS 240 in step S1203.

When the printing WS 240 receives the edit property candidate, theprinting WS 240 generates the print condition property candidate fromthe print property possessed in the printing WS 240 itself and the editproperty candidate informed from the image editing WS 241. This processis conducted as described in accordance with the flowchart shown in FIG.11.

After the printing WS 240 generates the print condition propertycandidate, the printing WS 240 sends the print condition propertycandidate by a SOAP message to the client PC 213 in step S1204.

By the above-described process, the client PC 213 can obtain the printcondition property candidate.

Next, the process concerning the print will be described with referenceto FIG. 63 and FIG. 64. In step S1205, the client PC 213 sends adocument ticket create request with an array of document IDs to therepository WS 235. In step S1206, the repository WS 235 sends a responsewith a document ticket with respect to the document ticket createrequest to the client PC 213.

In step S1207, the client PC 213 sends a document print request to theMFP-A 221. The document print request is sent by the SOAP message M21shown in FIG. 34, and the document ticket and the print condition areinformed to the MFP-A 221. In a case in FIG. 63, the client PC 213requests to paste the confidential stamp as the print conditionproperty.

When the printing WS 240 receives the document print request, theprinting WS 240 executes the process flow of the printing servicedescribed in FIG. 24. In step S1208, the printing WS 240 sends adocument edit request to the image editing WS 241. The document editrequest informs the document ticket and the edit contents.

Next, in step S1209, the image editing WS 241 sends a document ID obtainrequest included in the document ticket to the repository WS 235 inorder to get back (retrieve) the document from the repository WS 235.The image editing WS 241 obtains the document ID since the document isstored in the MFP-A 221 where the image editing WS 241 is implemented.The image editing WS 241 can edit the document corresponding to thedocument ID by obtaining the document ID.

Referring to FIG. 64, in step S1210, the repository WS 235 sends adocument ID to the image editing WS 241. The image editing WS 241 editsthe document and sends an edit result with an edited document to theprinting WS 240 (step S1211).

When the printing WS 240 receives the edited document, the printing WS240 prints out the edited document and sends a document print acceptresult to the client PC 213 in step S1212. The document print acceptresult is sent by the SOAP message described in FIG. 28.

The eighth embodiment is described above. Thus, the explanations fromthe first embodiment to the eighth embodiment are completed. From thefirst embodiment to the eighth embodiment, an outputting service part,an output condition property candidate obtain request receiving part, anoutput condition property candidate obtaining part, and an outputcondition property candidate obtaining part correspond to the printingWSF 226. An editing service part corresponds to the image editing WSF227. A Web service part corresponds to a Web service including the Webservice server (WSS) 224, the printing WSF 226, an the image editing WSF227.

An output service client part corresponds to the printing WSF 226. Anedit service client corresponds to the image editing WSF 227. A Webclient part corresponds to a Web service client including the Webservice client (WSC) 225, the printing WSF 226, and the image editingWSF.

FIG. 65 is a diagram showing a configuration in that a single Webservice client (WSC) can use a plurality of Web services (WS), accordingto the present invention. Referring to FIG. 65, the configuration willbe described in detail. The MFP-A 221 includes the printing WS 240 andthe image editing WS 241. Each of the printing WS 240 and the imageediting WS 241 functions as a Web service server for Web service clients(WS clients) 503 other than the MFP-A 221. Even in this case, both theprinting WS 240 and the image editing WS 241 can use the single Webservice client (WSC) 225, and each of the printing WS 240 and the imageediting WS 241 can use the repository WS 235 other than the MFP-A 221through the Web service client 225.

FIG. 66 is a diagram showing another configuration in that a single Webservice can use a plurality of Web service client (WSC), according tothe present invention. In FIG. 66, the MFP-B 222, the Web service client(WS client) 504, a UPnP repository WS 507, and a BMLinkS repository WS508 are shown.

BMLinkS is a standard specification defining a search of OA devices, adata format for the OA devices to send and receive data, and a controlof the OA devices.

In order to support the UPnP repository WS 507 and the BMLinkSrepository WS 508, which have a different protocol each other, a WSC_A505 for supporting a UPnP protocol and a WSC_B 506 for supporting aBMLinkS protocol are implemented in the MFP-B 222. Accordingly, forexample, the printing WS 240 being a server of the WS client 504 can useany one of the UPnP repository WS 507 and the BMLinkS repository WS 508.In addition, by implementing a Web service client (WSC) to support eachversion of the SOAP, it is possible to support each version of the SOAP.

FIG. 67 is a diagram showing a configuration formed by the MFP-Adescribed in FIG. 65 and the MFP-B described in FIG. 66, according tothe present invention. In FIG. 67, explanations of the parts describedabove will be omitted.

In the MFP-A 221 shown in FIG. 67, the printing WSF 226 and the imageediting WSF 227 can use the Web service client (WSC) 225 being a singleWeb service client. In addition, in the MFP-B 222, the printing WS 226can use two Web service clients: a Web service A client 501 and a Webservice B client 502. As described above, the Web service client (WSC)may be implemented for each specification of the Web service parts.

In the present invention, the output property includes at least one of acapability of setting copies of the document, a capability of setting asheet size to print out, a capability of printing both sides, acapability of collating copies, a capability of indicating a tray, acapability of printing multi-pages of the document on a single sheet, acapability of printing the document by a variable magnification, acapability of indicating a partial area in the document to print out, acapability of indicating a color print for the document, and acapability of setting a finisher.

In the present invention, the edit property includes as contents of theedit property, at lease one of a capability of pasting a stamp to thedocument, a capability of a drawing operation, a capability of deleting,copying, pasting, moving, or converting a color with respect to anindicated area, a capability of continuously editing multi-pages, and acapability of eliminating a stain of a ground color.

The present invention is not limited to the specifically disclosedembodiments, and variations and modifications may be made withoutdeparting from the scope of the present invention.

The present application is based on the Japanese Priority ApplicationsNo. 2003-376499 filed on Nov. 6, 2003, No. 2003-376500 filed on Nov. 6,2003, No. 2003-376501 filed on Nov. 6, 2003, No. 2004-318292 filed onNov. 1, 2004, No. 2004-318293 filed on Nov. 1, 2004, and No. 2004-318294filed on Nov. 1, 2004, the entire contents of which are herebyincorporated by reference.

1. An output information providing method for providing an edit propertyindicating edit contents executable for a document and an outputproperty indicating an output method executable when the document isoutput, said output information providing method comprising: receivingan output condition property candidate obtain request for obtaining anoutput condition property candidate; and providing the output conditionproperty candidate to a request originator sending the output conditionproperty candidate obtain request.
 2. The output information providingmethod as claimed in claim 1, further comprising obtaining the editproperty.
 3. The output information providing method as claimed in claim2, further comprising merging a plurality of edit properties to obtain amerged edit property when the plurality of edit properties are obtained.4. The output information providing method as claimed in claim 2,further comprising obtaining the output property.
 5. The outputinformation providing method as claimed in claim 4, further comprisingobtaining the output condition property candidate from the outputproperty and the edit property.
 6. The output information providingmethod as claimed in claim 5, wherein said providing the outputcondition property candidate provides edit information concerning anedit of the document as well as the property obtained by said obtainingthe output property, instead of providing the output condition propertycandidate.
 7. The output information providing method as claimed inclaim 1, wherein when the document is printed out, the output propertyincludes as contents of the output property at least one of a capabilityof setting copies of the document, a capability of setting a sheet sizeto print out, a capability of printing both sides, a capability ofcollating copies, a capability of indicating a tray, a capability ofprinting multi-pages of the document on a single sheet, a capability ofprinting the document by a variable magnification, a capability ofindicating a partial area in the document to print out, a capability ofindicating a color print for the document, and a capability of setting afinisher.
 8. The output information providing method as claimed in claim1, wherein the edit property includes as contents of the edit property,at lease one of a capability of pasting a stamp to the document, acapability of a drawing operation, a capability of deleting, copying,pasting, moving, or converting a color with respect to an indicatedarea, a capability of continuously editing multi-pages, and a capabilityof eliminating a stain of a ground color.
 9. An output informationproviding system for providing an output condition property candidateincluding an edit property indicating edit contents executable withrespect to a document and an output property indicating an output methodexecutable when the document is output, to a client requesting editingor outputting the document, said output information providing systemcomprising: an output condition property candidate obtain requestreceiving part receiving an output condition property candidate obtainrequest for obtaining an output condition property candidate from theclient; and an output condition property candidate providing partproviding the output condition property candidate to the client.
 10. Theoutput information providing system as claimed in claim 9, furthercomprising at least one Web service part providing a Web service. 11.The output information providing system as claimed in claim 10, furthercomprising a Web client part functioning as a client of said Web servicepart.
 12. The output information providing system as claimed in claim11, further comprising an outputting service part being the Web servicepart and obtaining the output property.
 13. The output informationproviding system as claimed in claim 12, further comprising an editingservice part being the Web service part and obtaining the edit property.14. The output information providing system as claimed in claim 12,further comprising an output service client part being the Web clientpart and obtaining the output property from said outputting servicepart.
 15. The output information providing system as claimed in claim13, further comprising an edit service client part being the Web clientpart and obtaining the edit property from said editing service part. 16.The output information providing system as claimed in claim 15, whereinsaid edit service client part obtains said edit property from at leastone of a plurality of the editing service parts.
 17. The outputinformation providing system as claimed in claim 13, wherein the editproperty includes as contents of the edit property, at lease one of acapability of pasting a stamp to the document, a capability of a drawingoperation, a capability of deleting, copying, pasting, moving, orconverting a color with respect to an indicated area, a capability ofcontinuously editing multi-pages, and a capability of eliminating astain of a ground color.
 18. The output information providing system asclaimed in claim 12, further comprising an output condition propertycandidate obtaining part obtaining the output condition propertycandidate from the output property obtained by said outputting servicepart and the edit property obtained by said editing service part. 19.The output information providing system as claimed in claim 18, whereinsaid output condition property candidate obtaining part merges theplurality of the edit properties to obtain a merged edit property, whena plurality of the edit properties are obtained.
 20. The outputinformation providing system as claimed in claim 18, wherein said outputcondition property candidate providing part provides the output propertyobtained by said outputting service part and edit information concerningan edit of the document, instead of providing the output conditionproperty candidate.
 21. The output information providing system asclaimed in claim 12, wherein when the document is printed out, theoutput property includes as contents of the output property at least oneof a capability of setting copies of the document, a capability ofsetting a sheet size to print out, a capability of printing both sides,a capability of collating copies, a capability of indicating a tray, acapability of printing multi-pages of the document on a single sheet, acapability of printing the document by a variable magnification, acapability of indicating a partial area in the document to print out, acapability of indicating a color print for the document, and acapability of setting a finisher.
 22. The output information providingsystem as claimed in claim 11, wherein said Web client part is providedfor each specification of the Web service parts.
 23. The outputinformation providing system as claimed in claim 22, wherein the eachspecification of the Web service parts is a version of a communicationprotocol.
 24. The output information providing system as claimed inclaim 10, wherein each of the Web client parts can use a plurality ofthe Web service part simultaneously.
 25. A document outputting methodfor editing and outputting a document, comprising: receiving an outputcondition property candidate obtain request including an output propertyindicating an outputting method executable when the document is output;providing the output condition property candidate to a requestoriginator sending the output condition property candidate; receiving adocument output request including an output condition being selectedfrom the output condition property; editing the document based on theoutput condition; and outputting the document being edited based on theoutput condition.
 26. The document outputting method as claimed in claim25, further comprising obtaining the edit property.
 27. The documentoutputting method as claimed in claim 26, further comprising obtaining amerged edit property in which a plurality of the edit properties aremerged when the plurality of the edit properties are obtained.
 28. Thedocument outputting method as claimed in claim 26, further comprisingobtaining the output property.
 29. The document outputting method asclaimed in claim 28, further comprising obtaining the output conditionproperty candidate from the output property and the edit property. 30.The document outputting method as claimed in claim 29, wherein saidproviding the output property candidate provides edit informationconcerning an edit of the document with the output property obtained insaid obtaining the output property, instead of providing the outputcondition property candidate.
 31. The document outputting method asclaimed in claim 26, wherein when the document is printed out, theoutput property includes as contents of the output property at least oneof a capability of setting copies of the document, a capability ofsetting a sheet size to print out, a capability of printing both sides,a capability of collating copies, a capability of indicating a tray, acapability of printing multi-pages of the document on a single sheet, acapability of printing the document by a variable magnification, acapability of indicating a partial area in the document to print out, acapability of indicating a color print for the document, and acapability of setting a finisher.
 32. The document outputting method asclaimed in claim 25, wherein the edit property includes as contents ofthe edit property, at lease one of a capability of pasting a stamp tothe document, a capability of a drawing operation, a capability ofdeleting, copying, pasting, moving, or converting a color with respectto an indicated area, a capability of continuously editing multi-pages,and a capability of eliminating a stain of a ground color.
 33. Thedocument outputting method as claimed in claim 25, wherein saidreceiving a document output request receives the document.
 34. Adocument outputting system for providing an edit property indicatingedit contents executable for a document and an output propertyindicating an outputting method executable when the document is outputto a client requesting outputting the document, said document outputtingsystem comprising: an output property candidate obtain request receivingpart receiving an output property candidate obtain request for obtainingan output condition property candidate from the client; an outputcondition property candidate providing part providing the outputcondition property candidate to the client; a document output requestreceiving part receiving a document output request including an outputcondition being selected from the output condition property candidate;an editing service part editing the document based on the outputcondition; and an outputting service part outputting the document beingedited based on the output condition.
 35. The document outputting systemas claimed in claim 34, further comprising an output property obtainingpart obtaining the output property.
 36. The document outputting systemas claimed in claim 35, further comprising an output service client partobtaining the output property from the output property obtaining part.37. The document outputting system as claimed in claim 34, furthercomprising an edit property obtaining part obtaining the edit property.38. The document output system as claimed in claim 37, furthercomprising an edit service client part obtaining the edit property fromsaid edit property obtaining part.
 39. The document outputting system asclaimed in claim 37, further comprising an output condition propertycandidate generating part generating the output condition propertycandidate from the output property obtained by said output propertyobtaining part and the edit property obtained by said edit propertyobtaining part.
 40. The document outputting system as claimed in claim39, wherein said output condition property candidate generating partgenerates a merged edit property in which a plurality of the editproperties are merged when the plurality of the edit properties arereceived.
 41. The document outputting system as claimed in claim 39,wherein said output condition property candidate providing part providesthe output property obtained by an output property obtaining part andedit information concerning an edit of the document, instead ofproviding the output condition property candidate.
 42. The documentoutputting system as claimed in claim 37, wherein the edit propertyincludes as contents of the edit property, at lease one of a capabilityof pasting a stamp to the document, a capability of a drawing operation,a capability of deleting, copying, pasting, moving, or converting acolor with respect to an indicated area, a capability of continuouslyediting multi-pages, and a capability of eliminating a stain of a groundcolor.
 43. The document outputting system as claimed in claim 34,wherein when the document is printed out, the output property includesas contents of the output property at least one of a capability ofsetting copies of the document, a capability of setting a sheet size toprint out, a capability of printing both sides, a capability ofcollating copies, a capability of indicating a tray, a capability ofprinting multi-pages of the document on a single sheet, a capability ofprinting the document by a variable magnification, a capability ofindicating a partial area in the document to print out, a capability ofindicating a color print for the document, and a capability of setting afinisher.